User's Guide

Problem solving

This chapter contains procedures that help you troubleshoot problems and optimize the performance of your adapter.

Starting the troubleshooting process

If you cannot successfully install the adapter or the adapter does not operate properly, perform the following steps:

• If yours is the first station on the ring, make sure that AutoSense is disabled.
• Refer to the following table. Locate the symptom that best describes the problem.

This chapter includes the following topics:

Section	Page
Troubleshooting Utility	"Troubleshooting Utility"
Running adapter diagnostics	"Running adapter diagnostics"
Understanding the adapter LEDs and labels	"Understanding the adapter LEDs and labels"
Solving problems with driver installation	"Solving problems with driver installation"
Solving an adapter communication problem	"Solving an adapter communication problem"
Using PCISETUP	"Using PCISETUP"
Contacting IBM product support	"Contacting IBM product support"
Downloading code from the Web	"Downloading code from the Web"
Tech tips and frequently asked questions	"Tech tips and frequently asked questions"
Other performance enhancements	"Other performance enhancements"

Troubleshooting Utility

Troubleshooting Utility is an application that you can use to collect information about your system to help diagnose problems with your token-ring PCI adapter. It is available for the following systems:

• Windows 95 OSR2
• Windows 98
• Windows NT 4.0
• Windows 2000
• Windows Millennium

Troubleshooting Utility helps you identify and solve network problems that involve the adapter. It analyzes your system and all IBM token-ring PCI adapters in your system. Using the available information, it offers suggestions for solving your networking problems. Troubleshooting Utility also generates an adapter information report that provides detailed information about your system to enable your network administrator or other support personnel to efficiently assist you. You can also use it to create a diagnostic diskette.

With Troubleshooting Utility Version 1.10 or later, running on Windows 98, Windows ME, Windows 2000., or later, the Advanced Diagnostics can be run from directly within the Troubleshooting Utility instead of having to reboot to a diagnostics diskette. In addition, you can also update the microcode on your PCI adapters. Windows device driver Version 5.33 or later is required in order to permit Troubleshooting Utility Version 1.10 or later to perform the advanced diagnostic and microcode update functions.

If Troubleshooting Utility verifies that your adapter is working correctly, yet you are still having networking problems, you should use Windows Help to verify that the correct services and protocols are installed for your network.

Installing Troubleshooting Utility

You need the self-extracting installation package TRSHOOT.EXE in order to install Troubleshooting Utility. You can obtain this package from the adapter CD-ROM or the Web. For Windows 9x systems, the package automatically installs an IBM LAN Adapter Management IOCTL driver as a Windows protocol.

To install Troubleshooting Utility, run the software package executable and follow the instructions on the installation wizard windows.

A folder containing Troubleshooting Utility, Troubleshooting Utility Help, and a deinstall icon are copied to your computer.

Starting Troubleshooting Utility

You can use Troubleshooting Utility in the wizard mode or expert mode. The wizard mode provides a series of windows that guide you through the troubleshooting process. The expert mode is for more advanced users.

To start Troubleshooting Utility, perform the following steps.

1. Select Start > Programs > Troubleshooting Utility > Troubleshooting Utility.
2. Select one of the following options:
   • Select the Wizard button to run the Wizard. The Wizard provides a series of windows that guide you through the troubleshooting process.
   • Select the Expert button to display a dialog box with tabs for each troubleshooting process task.

Using Troubleshooting Utility

In the wizard mode, Troubleshooting Utility displays windows for performing troubleshooting tasks.

In the expert mode, Troubleshooting Utility displays a dialog box with tabs for performing troubleshooting tasks.

Window / Tab	Task
Adapter Analysis	Summarizes the adapter's operational status. SeeViewing adapter analysis information.
NIC Status	Displays status information about the instances of the drivers installed in your system. See Viewing NIC status.
Event Log	Displays any logged messages about your adapter. See Viewing the event log.
Build Diagnostic Diskette (with Troubleshooting Utility Version 1.10 or later, this option is present only on Windows 95 and Windows NT4)	Gives you access to functions for building a diagnostic diskette. See Building a diagnostic diskette.
Contact Information	Provides a place to enter your name, address, telephone number, and customer report ID (if one has previously been assigned by support personnel). This information is printed on the adapter information report. See Entering contact information.
Adapter Information Report	Gives you access to the functions for generating a report containing information collected about your system. The information in this report is may be useful to support personnel in diagnosing problems with your adapter. See Generating an adapter information report.
Advanced Diagnostics (available only with Troubleshooting Utility Version 1.10 and later, and only when used with Windows 98, Windows ME, Windows 2000, and later, in conjunction with Windows device driver version 5.33 or later. NOT available when used with Windows 95 or Windows NT4)	Provides the ability to run the adapter diagnostics (16/4, 100; ring test or wrap test) directly from within the Troubleshooting Utility while running Windows, rather than having to boot to a diagnostic diskette or CD-ROM. See "Running adapter diagnostics" on page 45. See Running advanced diagnostics.
Microcode Update (available only with Troubleshooting Utility Version 1.10 and later, and only when used with Windows 98, Windows ME, Windows 2000, and later, in conjunction with Windows device driver version 5.33 or later. NOT available when used with Windows 95 or Windows NT4)	Gives you the ability to update your microcode while under Windows rather than updating from a DOS diskette. See Updating microcode.

Viewing adapter analysis information

Adapter analysis information displays on the first window that appears when you run Troubleshooting Utility Wizard. This information is also displayed on the NIC Status tab when you run Troubleshooting Utility in the expert mode.

Troubleshooting Utility analyzes your system and all token-ring PCI adapters in your system. For each adapter found, the adapter's burned-in address (mac address) and current operating status is displayed. A summary of the operational status and suggestions for correcting problems are displayed.

Viewing NIC status

The information displayed on the NIC Status tab might help you to quickly identify a problem. The NIC Instance list box contains a list of the adapters that are found in your system. This list is obtained from the registry.

On Windows NT 4.0 systems, the token-ring PCI adapters are listed in: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows_NT\CurrentVersion\ NetworkCards. The token-ring PCI instances are listed in: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\IBMTRP.

On Windows 9x systems, the token-ring PCI instances are listed in: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Net\.

On Windows 2000 systems, the token-ring PCI instances are listed in: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Network Cards\# in the registry variable 'ServiceName'.

To view NIC status, complete the following steps:

1. Click the arrow beside Select NIC Instance to display a list of all NIC instances.
2. Click the instance you want to troubleshoot.

   The information for the instance you selected displays in the fields. This information includes:

   • MAC address. This is the address of the NIC encoded in the adapter memory at the factory. This address can also be found on the adapter card label. This is a unique address that the network software uses to distinguish the adapter from others in the network
   • Transmit/Receive Test. The transmit/receive test indicates the number of packets being transmitted and received without errors by the adapter. These counters are updated approximately every 2 seconds. If the transmit and receive fields are being incremented, traffic is being processed by the adapter. If no other stations are on the ring, these counters will increment very slowly.
   • Hardware status. This is the current status of the NIC. The status is represented by the following values that correspond to the NDIS_HARDWARE_STATUS-type values:
     

     Status	NDIS_HARDWARE_STATUS-type value	Explanation
     Ready	NdisHardwareStatusReady	The NIC is available and capable of sending and receiving data over the wire.
     Initializing	NdisHardwareStatusInitializing	The NIC is initializing.
     Resetting	NdisHardwareStatusReset	The NIC is resetting.
     Closing	NdisHardwareStatusClosing	The NIC is closing.
     Not Ready	NdisHardwareStatusNotReady	The NIC is closed, shut down, or broken.

   • Ring state. This is the state of the NIC with respect to entering the ring. The ring state is represented by the following values that correspond to the NDIS_802_5_RING_STATE values:
     

     Status	NDIS_802_5_RING_STATE value	Explanation
     Open	NdisRingStateOpened	This specifies an open ring.
     Closed	NdisRingStateClosed	This specifies a closed ring.
     Opening	NdisRingStateOpening	This specifies a ring that is opening.
     Closing	NdisRingStateClosing	This specifies a failure of a ring open operation.
     Open Failure	NdisRingStateOpenFailure	The NIC is closed, shut down, or broken
     Ring Failure	NdisRingStateRingFailure	This specifies a failure of a ring.

   • Ring status. This indicates the last ring status, which corresponds to the NDIS token-ring ring status codes (OID_802_5_CURRENT_RING_STATUS) as listed in the following table:
     

     Status	OID_802_5_CURRENT_RING_STATUS
     Signal Loss	NDIS_RING_SIGNAL_LOSS
     Hard Error	NDIS_RING_HARD_ERROR
     Soft Error	NDIS_RING_SOFT_ERROR
     Transmit Beacon	NDIS_RING_TRANSMIT_BEACON
     Wire Fault	NDIS_RING_LOBE_WIRE_FAULT
     Auto Removal Error	NDIS_RING_AUTO_REMOVAL_ERROR
     Remove Received	NDIS_RING_REMOVE_RECEIVED
     Counter Overflow	NDIS_RING_COUNTER_OVERFLOW
     Single Station	NDIS_RING_SINGLE_STATION
     Ring Recovery	NDIS_RING_RING_RECOVERY

   • Analysis. A summary of the operational status and suggestions for correcting problems are displayed in this section of the NIC Status tab.

Viewing the event log

The event log displays all messages relating to the token-ring PCI adapters that have been generated since the last reboot of the machine. On NT systems, these messages are parsed from the Event Viewer, which is an NT Common Administrative Tool. On Windows 9x systems, these messages are parsed from the NDISLOG.txt file. This screen or tab is displayed only when there are messages to present. If no token-ring PCI events have been generated since the system was last rebooted, the screen or tab is not displayed.

Building a diagnostic diskette

With Troubleshooting Utility Version 1.10 or later, this option is present only on Windows 95 and Windows NT4. For Windows 98, Windows 2000, Windows ME, and later, see Running advanced diagnostics.

Note:

You can either build a diagnostic diskette to use for running diagnostics or use the bootable CD-ROM that came with your adapter to run diagnostics. To use the CD-ROM, your computer must have a bootable CD-ROM drive. The CD-ROM option allows you to perform diagnostics on a computer that does not have a diskette drive.

To build a diagnostic diskette, perform the following procedure:

1. Insert a blank, high-density diskette into your diskette drive (usually drive A).
2. Click the Build button to build the diagnostic diskette.

   When the build is finished, you can run the diagnostics immediately if you want.

3. To run the diagnostics, leave the diskette in the diskette drive and click the Reboot button.

   When you click the Reboot button, your computer automatically reboots before running the diagnostics. For detailed information about running the diagnostics, see Running adapter diagnostics.

   When you finish running diagnostics, the system prompts you to remove the diskette and reboot the system. After the system reboots, Troubleshooting Utility resumes execution.

Entering contact information

The information you enter on this tab is printed on the adapter information report. For information on creating this report, see Generating an adapter information report.

To enter support information, complete the following steps:

1. Type your name, e-mail address, and telephone number in the fields provided.
2. If you have already reported your problem and received a customer report ID, type the customer report ID. If you do not have a customer report ID, leave this field blank.
3. Type a brief description of the problem.
4. Click Yes or No to indicate whether or not this is a new install.
5. Click Yes or No to indicate whether or not you have run the diagnostic diskette.

   For information on building a diagnostic diskette, see Building a diagnostic diskette.

Generating an adapter information report

The adapter information report contains information about the devices installed in your computer, including the adapters. The information collected in this report might be useful in determining the cause of a networking problem. Included is the following information:

• Operating system information
• Information about your computer such as model and BIOS level
• List of PCI device drivers installed in your system
• Detailed information about each PCI device such as PCI bus configuration

The information is copied to a file called ADPTINFO.PCI. This file is saved on the root directory of drive C. However, on Windows NT systems that have NTFS on drive C, the ADPTINFO.PCI file is saved to a FAT formatted diskette in drive A.

To generate the report, perform the procedure that is applicable to your operating system.

Windows 9x

To generate an adapter information report on Windows 9x, perform the following steps.

1. Click the Generate button to create the report file (ADPTINFO.PCI).
2. Click the Print button to print the report on your default printer.

Windows NT

To generate an adapter information report on Windows NT, perform the following steps.

1. Insert a blank, high-density diskette into your diskette drive (usually drive A).
2. Select the BUILD button to build the pci_info diskette.
3. Select the REBOOT button to generate the adapter information report.
4. When prompted, remove the diskette from drive A and reboot your computer.

   When NT starts, Troubleshooting Utility resumes.

5. Click the PRINT button to print the report on your default printer. If the file system on drive C is NTFS, you must reinsert the pci_info diskette into your diskette drive.

Running advanced diagnostics

This feature is available only with Troubleshooting Utility Version 1.10 or later, and only when used with Windows 98, Windows ME, Windows 2000, and later, in conjunction with Windows device driver version 5.33 or later. For Windows 95 or Windows NT4, see Building a diagnostic diskette. For details on running the advanced diagnostics from within the Troubleshooting Utility, see Running 4/16 Mbps diagnostics beginning with step 3, or Running 100-Mbps diagnostics beginning with step 3.

Updating microcode

Sometimes it is necessary to update the microcode (also referred to as firmware) on your IBM PCI Token-Ring family adapter. In certain environments, you can update your microcode from within Windows, rather than having to boot a DOS diskette. This is especially useful for systems that either do not have a floppy disk or the system is not configured to boot from a floppy disk. Performing a microcode update from the Troubleshooting Utility will close your network adapter and remove your computer from the network while the microcode update occurs. You will need to reboot your computer to complete the microcode update process. Because you must reboot your computer, it is important to save all open files and close all open applications before a microcode update is initiated.

You can use the Troubleshooting Utility to update the microcode on your IBM PCI Token-Ring family adapter under the following conditions:

• The computer is running Windows 98, Windows ME, or Windows 2000 (or later)
• You have one of the following Token-Ring adapters:
  • IBM 16/4 Token-Ring PCI Adapter 2
  • IBM 16/4 Token-Ring PCI Adapter 2 with Wake on LAN
  • IBM 16/4 Token-Ring PCI Special
  • IBM High-Speed 100/16/4 Token-Ring PCI Adapter
  • IBM 16/4 Token-Ring Low Profile PCI Management Adapter
  • IBM 16/4 Token-Ring PCI Management Adapter
  • IBM High-Speed 100/16/4 Token-Ring PCI Management Adapter
• You are running the Troubleshooting Utility in Expert mode
• The adapter is fully functional (for example, no problems are reported in NIC Status)

To update the microcode, you must first obtain the new level of microcode. Updated microcode can be obtained from http://www.networking.ibm.com/support or from your system administrator. After the desired level of microcode has been obtained, perform the following steps:

1. Start the Troubleshooting Utility from the start menu.
2. At the welcome screen, click on Expert.

   Note:

   You cannot update microcode using Wizard mode

3. Click on the Microcode Update tab. You are prompted to select the folder that contains the updated microcode images that you previously obtained from http://www.networking.ibm.comor your system administrator. The microcode images can be located on your hard drive, on a diskette drive, on a network drive, or from Network Neighborhood (on Windows 98) or My Network Places (on Windows ME and Windows 2000).
4. From the Adapter box, select the adapter you want to update. If the selected adapter is supported (see the previous list of supported adapters) then the name of the adapter will appear in the Adapter Name box. Additionally, the microcode level and an analysis of the situation will appear.

Running adapter diagnostics

Attention: To avoid potentially erroneous results, you should always perform a power-on reboot of your computer before running the diagnostics from a bootable diskette or CD-ROM. This is not required when running diagnostics from within the Troubleshooting Utility.

Creating a diagnostic diskette

You can create a diagnostic diskette in either of two ways:

• Download and run the DIAGDISK.EXE located on the adapter CD-ROM.
  1. Insert a blank, high-density diskette into your diskette drive (usually drive A).
  2. Point your Web browser to x:\startcd.htm on the CD-ROM (where x is your CD-ROM drive).
  3. Select your adapter and click Downloads.
  4. Select Diagnostics to download the executable.
  5. Run the executable to create the diagnostic diskette.
• Use Troubleshooting Utility to create the diskette. See Building a diagnostic diskette.

Running 4/16 Mbps diagnostics

Use the following procedure to run 4/16 Mbps diagnostics:

1. Insert the diagnostic diskette in drive A and reboot your computer.
2. At the DOS Boot Menu, select IBM PCI adapter family extended diagnostics for 16 Mb/s and 4 Mb/s.

   If the system will not boot with the adapter installed, but will boot without the adapter, skip to step 6.

3. If there is more than one adapter installed in your computer, a selection menu displays each adapter by its universally administered address. Use the cursor keys or the mouse to select the adapter to test.
4. Connect the adapter to the network and press the Enter key to select Test.

   There are two test options: wrap test and on-ring test.

   • The wrap test tests the adapter and cable through the hub or concentrator, or through a wrap plug attached to the cable.
   • For the on-ring test, the adapter must be connected to a network with other adapters, so the ring speed of the network can be automatically sensed. If the adapter is the only one in the network, the on-ring test will fail.
5. Select the option for the test to perform.
6. If the test indicates that there is no adapter in the system, or that diagnostics cannot be run:
   • Check that the adapter is correctly seated in the slot.
   • Make sure that the LEDs blink alternately amber and green after you power up your computer.
   • See Table 5 for LED states.
   • Run the adapter diagnostics again. If the tests are completed successfully, and your computer still is not communicating, contact your network administrator.
7. If the wrap test and on-ring test run without errors, the adapter is ready for use. Exit the diagnostic program, and follow the directions for reactivating the computer.

   If an error occurs, record any messages that appear, record the LED sequences, and contact your network administrator.

   Note:

   This procedure does not verify that the data rate of the device driver setting matches the data rate of the LAN segment unless the diagnostics are run from within the Troubleshooting Utility Version 1.10 or later..

Running 100-Mbps diagnostics

Use the following procedure to run 100-Mbps diagnostics:

1. Insert the diagnostic diskette in drive A and reboot your computer.
2. At the DOS Boot Menu select IBM PCI adapter family extended diagnostics for 100 Mb/s only.
3. If there is more than one adapter installed in your computer, a selection menu displays each adapter by its universally administered address. Use the cursor keys or the mouse to select the adapter to test.
4. Disconnect the adapter to be tested from the 100-Mbps port.
5. Connect a wrap plug into the RJ-45 jack.
6. Select the Wrap test and select Start Test.
7. If the test indicates that there is no adapter in the system, or that diagnostics cannot be run:
   • Check that the adapter is correctly seated in the slot.
   • Make sure that the LEDs blink alternately amber and green after you power up your computer.
   • See Table 5 for LED states.
   • Run the adapter diagnostics again. If the tests are completed successfully, and your computer still is not communicating, contact your network administrator.
8. If the diagnostics runs without errors, the adapter is ready for use. Exit the diagnostics program and follow the instructions to reboot the computer. If an error occurs, record any messages that appear, record the LED sequences, and contact your network administrator.

Understanding the adapter LEDs and labels

Figure 4 and Table 5 describe the LEDs and labels located on the bracket of the adapter.

Figure 4. The adapter LEDs and labels

Understanding the adapter LEDs

The LEDs provide information useful for monitoring the status of the adapter and for solving problems. If the green LED is on and the amber LED is off, the adapter is operating correctly. If the amber LED is blinking and the green LED is on, a problem with the adapter has been detected. Table 5 indicates the sequence that displays when the you start the computer and the adapter reaches the open state successfully. Some of the states might be too brief to observe.

Table 5. Startup sequence of LED states

Amber	Green	Explanation
Blinking	Blinking	Slow blink. The adapter is waiting for initialization. Fast blink. The adapter has detected a wake-up frame and is attempting to wake up the system. If this state persists, it indicates one of the following problems: The attached PC does not have Wake on LAN enabled. To correct this problem, power on the PC and enable the Wake on LAN feature from the power management system configuration menu. The Wake on LAN cable is not attached correctly. To correct this problem, ensure that the Wake on LAN cable is properly attached.
Off	Off	The adapter initialization is in progress, or the computer is powered off.
Off	Blinking	The adapter did not detect any problems during its self-diagnostic tests and is waiting to open. If this LED state occurs after the adapter has been opened, this state indicates that the adapter has been closed under software control.
Off	On	The adapter is open and operating correctly.

Table 6 lists LED states that indicate problems.

Table 6. Problems shown by adapter LED states

Amber	Green	Explanation	Action
On	Off	The adapter self-diagnostic tests failed or there is a problem with the adapter.	Go to Running adapter diagnostics to test the adapter.
Blinking	Off	The adapter is closed due to one of the following conditions: The adapter open failed. The adapter detected a wire fault. The adapter failed the auto-removal test.	Perform the following procedures, as appropriate: Go to Solving an adapter communication problem. Verify that the adapter is configured correctly. If other stations on the network are having problems communicating, contact your network administrator.
Blinking	On	The adapter has detected beaconing or a hard error.	Go to Solving an adapter communication problem
On	On	The adapter has failed before running the self-diagnostic tests.	Go to Running adapter diagnostics to test the adapter.

See Glossary for definitions of the terms used in Table 6.

Understanding the adapter labels

The green dot label indicates the speeds that this adapter supports over a token ring.

The universally administered address label contains the adapter's universally administered address. This is the MAC address that was encoded in the adapter memory at the factory. This 12-digit, hexadecimal address is recorded on the label in groups of two digits from left to right, starting on the first row. In Figure 4, the universally administered address is X'00 06 2E 00 00 01' in non-canonical format, with the most significant bit (MSB) first. The universally administered address is unique and is used by network software to distinguish the adapter from others in the network. If you prefer the adapter to be known on the network by a locally administered address, you must configure the device driver or protocol driver to use a locally administered address.

Solving problems with driver installation

If you have a problem with installing a driver, perform the following procedure.

1. Make sure that you correctly followed the instructions for installing the adapter.
2. In the following table, locate the row that describes the network operating system or network application on the computer and perform the recommended actions.

Solving an adapter communication problem

Check the following list of possible causes if the adapter is unable to communicate on the network but other stations on the network are able to communicate.

1. Verify that the appropriate cable is connected to the adapter and to the network. See Selecting adapter cables for a description of the compatible cables.
2. Verify that the adapter is firmly seated in the expansion slot.
3. Verify that the setting for the adapter's Data Rate option matches the data rate of the network, or that the data rate has been set to AutoSense if yours is not the first station on the ring. Run the software configuration again to determine the current setting.
4. Replace the adapter cable with one that is known to be good.

Using PCISETUP

The PCISETUP program is provided as an executable program on the CD-ROM in the x:\pcisetup directory.

The program looks for specific system chips based on their PCI Vendor ID and Device ID. Based on which chips are found, modifications are made to specific bits within that chip's PCI configuration registers.

If there is already a version of PCISETUP installed on your computer, and you are adding a new token-ring adapter, you might need to replace the PCISETUP file in your computer with the PCISETUP file on the CD-ROM to ensure you are using the latest version number.

PCISETUP modifies the BIOS setup for the adapter in specific systems.

If you need to install a PCISETUP file, use the instructions that are applicable to your operating system.

DOS, Novell, Windows, or Windows 95 (adapter driver not in CONFIG.SYS)

1. Insert the CD-ROM in the drive.
2. Copy x:\pcisetup\pcisetup.exe (where x is your CD-ROM drive) to the root directory of the diskette from which the system boots.
3. Make the following line the first executable line in the AUTOEXEC.BAT file:

   PCISETUP
   

DOS, Novell, Windows, or Windows 95 (adapter driver in CONFIG.SYS)

1. Insert the CD-ROM in the drive.
2. Copy x:\pcisetup\pcisetup.dos (where x is your CD-ROM drive) to the root directory of the diskette from which the system boots.
3. Make the following line the first executable line in the CONFIG.SYS file:

   DEVICE=PCISETUP.DOS
   

OS/2

1. Insert the CD-ROM in the drive.
2. Copy x:\pcisetup\pcisetup.os2 (where x is your CD-ROM drive) to the root directory of the disk from which the system boots.
3. Make the following line the first executable line in the CONFIG.SYS file:

   DEVICE=PCISETUP.OS2
   

Windows NT

1. Insert the CD-ROM in the drive.
2. From the File pull-down menu, select Run.
3. Type x:\pcisetup\pcisetnt (where x is your CD-ROM drive) in the path entry field.
4. Select OK.

   PCISETNT.BAT will install PCISETUP.SYS as a device driver that will be loaded each time the system is started.

Contacting IBM product support

You can call the following telephone numbers for product support:
1-800-237-5511 IBM Support Services (U.S. only)
1-800-772-2227 IBM HelpCenter^(R) (U.S. only)
1-800-565-3344 HelpPC (Canada)

Customers outside the U.S. and Canada should contact their place of purchase.

Downloading code from the Web

You can download the latest code from the following location on the Web:

  http://www.ibm.com/networking/support

Tech tips and frequently asked questions

To find tips about specific hardware and software situations, go to x:\startcd.htm on the CD-ROM (where x is your CD-ROM drive.)

Other performance enhancements

There is a white paper on this subject at the following location on the Web:

http://www.ibm.com/networking/per/per10.html